Teaching Methodology

This course is based on the principles of OWNERSHIP. The success of passing the course lies on YOU (the student). Thus, you are responsible for your learning, decisions and actions. After all, evidence of learning will be demonstrated based on the quality of deliverables that will be submitted to the class.
The course is meant to be exploratory, i.e., understanding Web Science and aligning it with the interest of the students. Part of the learning assessment is conversation.

Project-based Learning Approach

A portion of this course is project-driven, i.e., the basis of the grade would depend on the deliverables of a project. Specifications and deadlines will be provided during the semester. Choice of simple project is as follows:
  • Semantic Technology
  • Web Crawler with Visualization

Portfolio using Wikispaces

You are required to have a wiki located at www.wikispaces.com. Make me a collaborator using the rcsolamo account name. A link to your wiki will be placed at the course wiki. Create the following pages:
  • Home Page. You can personalized this page by indicating your student number and name. Also, include in this page the following paragraph:

This is a course requirement of CS 268 Web Science of the Department of Computer Science, College of Engineering, UP Diliman Quezon City, Philippines, under the guidance of Prof. Ma. Rowena C. Solamo for the 2nd semester of the academic year 2011-2012.

  • MyOwnNotes Page.
  • MyOwnDesign Page.
  • MyOwnImplementation Page.
    The motivation is to make studying Web Science as a personalized learning.

R2D2 Teaching Methodology (Read, Reflect, Display, Do)

Four learning activities that will foster life-long learning will be done by the student. They are:
  • Read
    • You are required to read, view or listen to the resource available in the class wiki. You are required to read two (2) papers from proceedings and journals. Papers are available in the library or online via UP's DilNet. [http://www.mainlib.upd.edu.ph/?q=online-subscriptions]. Preferred papers are from IEEE or ACM.
  • Reflect
    • MyOwnNotes Page of your wiki. Here you will write summary of what you understand about resources read, viewed or listened to, including the additional readings. It is preferred that your notes are accompanied by a concept map.
MyOwnNotes Evaluation Criteria - >
  • Display
    • MyDesign Page contains the design of the project portion of the course. [Specifications to follow].
  • Do
    • MyImplementation Page contains the implementation of the project portion of the course. [Specifications to follow.]

Grade Requirements

Requirements:


Journal (MyOwnNotes)- 60%
Design (MyOwnDesign)- 15%
Implementation (MyOwnCodes)- 15%
Project Presentation- 05%
Individual Assessment - 05%

Total: 100%

Grading System:


GENERAL AVERAGE FINAL GRADE
92 - 100 1.00
88 - <92 1.25
85 - <88 1.50
82 - <85 1.75
78 - <82 2.00
74 - <78 2.25
70 - <74 2.50
65 - <70 2.75
60 - <65 3.00
below 60 5.00


Passing Mark: 3.0

Class Policies

Attendance:

Attendance is checked. A student is allowed a maximum of 6% of the total course time (6 meetings). A student exceeding the maximum number of allowable absences will be given a grade 5.0 if he or she does not drop the course or file for LOA (Leave of absence). A student is considered to have dropped the course only upon the submission of the instructor’s copy of the dropping slip. Otherwise, he or she will be given the corresponding grade. It is the responsibility of the student to catch up with lessons missed.
Deadline for Dropping is on February 20, 2012.
Deadline for Filing of LOA is on March 5, 2012.


Intellectual Dishonesty:

Cheating and Plagiarism is not allowed and punishable. If caught, you automatically get 5.0 in this course and may be charged and suspended or expelled if found guilty.
For Summary of Papers, you are requested to cite all resources used. You should follow ACM format for referencing resources.

For Projects you are allowed to:
  • study codes or existing solutions found in the internet but not allowed to pass it as your work. If you need to use such codes or existing solutions, you need to comply with copyrights (such as asking for written permission) or copylefts (give attribution). You also need to cite the source, and place such citation in your wiki and codes. The format is as follows:

<name of author (lastname, first name)>.<name of webpage>. Last accessed: <date of last access>.

  • study codes or existing solutions from bound sources such as books, journals etc. Again, they need to be cited. The format is as follows:

<name of author (lastname, first name)>.<title>. <publisher> . <year published>.

  • study codes or existing solutions of classmates and friends provided permission is granted. Again, if you need to use such code or existing solution, you need to comply with copyrights (such as asking written permission). You also need to cite the source, and place such citation in your wiki or codes. The format is as follows:

<name of student/friend>.<name of MP/ME/SP>. <semester>AY<year>.Requirement for <subject>.

Finally, all design and implementation you have created should be licensed. More specifically, it should use the GPL license (open source). Details of licensing your design and implementation will be discussed later on.